<!DOCTYPE html>
<html>
<!-- Created by GNU Texinfo 7.1.1, https://www.gnu.org/software/texinfo/ -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<!-- This file documents the use of the GNU compilers.

Copyright © 1988-2023 Free Software Foundation, Inc.

Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "Funding Free Software", the Front-Cover
Texts being (a) (see below), and with the Back-Cover Texts being (b)
(see below).  A copy of the license is included in the section entitled
"GNU Free Documentation License".

(a) The FSF's Front-Cover Text is:

A GNU Manual

(b) The FSF's Back-Cover Text is:

You have freedom to copy and modify this GNU Manual, like GNU
     software.  Copies published by the Free Software Foundation raise
     funds for GNU development. -->
<title>Function Names (Using the GNU Compiler Collection (GCC))</title>

<meta name="description" content="Function Names (Using the GNU Compiler Collection (GCC))">
<meta name="keywords" content="Function Names (Using the GNU Compiler Collection (GCC))">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta name="viewport" content="width=device-width,initial-scale=1">

<link href="index.html" rel="start" title="Top">
<link href="Indices.html" rel="index" title="Indices">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="C-Extensions.html" rel="up" title="C Extensions">
<link href="Return-Address.html" rel="next" title="Return Address">
<link href="Incomplete-Enums.html" rel="prev" title="Incomplete Enums">
<style type="text/css">
<!--
a.copiable-link {visibility: hidden; text-decoration: none; line-height: 0em}
div.example {margin-left: 3.2em}
kbd.key {font-style: normal}
span:hover a.copiable-link {visibility: visible}
-->
</style>


</head>

<body lang="en_US">
<div class="section-level-extent" id="Function-Names">
<div class="nav-panel">
<p>
Next: <a href="Return-Address.html" accesskey="n" rel="next">Getting the Return or Frame Address of a Function</a>, Previous: <a href="Incomplete-Enums.html" accesskey="p" rel="prev">Incomplete <code class="code">enum</code> Types</a>, Up: <a href="C-Extensions.html" accesskey="u" rel="up">Extensions to the C Language Family</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Indices.html" title="Index" rel="index">Index</a>]</p>
</div>
<hr>
<h3 class="section" id="Function-Names-as-Strings"><span>6.50 Function Names as Strings<a class="copiable-link" href="#Function-Names-as-Strings"> &para;</a></span></h3>
<a class="index-entry-id" id="index-_005f_005ffunc_005f_005f-identifier"></a>
<a class="index-entry-id" id="index-_005f_005fFUNCTION_005f_005f-identifier"></a>
<a class="index-entry-id" id="index-_005f_005fPRETTY_005fFUNCTION_005f_005f-identifier"></a>

<p>GCC provides three magic constants that hold the name of the current
function as a string.  In C++11 and later modes, all three are treated
as constant expressions and can be used in <code class="code">constexpr</code> constexts.
The first of these constants is <code class="code">__func__</code>, which is part of
the C99 standard:
</p>
<p>The identifier <code class="code">__func__</code> is implicitly declared by the translator
as if, immediately following the opening brace of each function
definition, the declaration
</p>
<div class="example smallexample">
<pre class="example-preformatted">static const char __func__[] = &quot;function-name&quot;;
</pre></div>

<p>appeared, where function-name is the name of the lexically-enclosing
function.  This name is the unadorned name of the function.  As an
extension, at file (or, in C++, namespace scope), <code class="code">__func__</code>
evaluates to the empty string.
</p>
<p><code class="code">__FUNCTION__</code> is another name for <code class="code">__func__</code>, provided for
backward compatibility with old versions of GCC.
</p>
<p>In C, <code class="code">__PRETTY_FUNCTION__</code> is yet another name for
<code class="code">__func__</code>, except that at file scope (or, in C++, namespace scope),
it evaluates to the string <code class="code">&quot;top level&quot;</code>.  In addition, in C++,
<code class="code">__PRETTY_FUNCTION__</code> contains the signature of the function as
well as its bare name.  For example, this program:
</p>
<div class="example smallexample">
<pre class="example-preformatted">extern &quot;C&quot; int printf (const char *, ...);

class a {
 public:
  void sub (int i)
    {
      printf (&quot;__FUNCTION__ = %s\n&quot;, __FUNCTION__);
      printf (&quot;__PRETTY_FUNCTION__ = %s\n&quot;, __PRETTY_FUNCTION__);
    }
};

int
main (void)
{
  a ax;
  ax.sub (0);
  return 0;
}
</pre></div>

<p>gives this output:
</p>
<div class="example smallexample">
<pre class="example-preformatted">__FUNCTION__ = sub
__PRETTY_FUNCTION__ = void a::sub(int)
</pre></div>

<p>These identifiers are variables, not preprocessor macros, and may not
be used to initialize <code class="code">char</code> arrays or be concatenated with string
literals.
</p>
</div>
<hr>
<div class="nav-panel">
<p>
Next: <a href="Return-Address.html">Getting the Return or Frame Address of a Function</a>, Previous: <a href="Incomplete-Enums.html">Incomplete <code class="code">enum</code> Types</a>, Up: <a href="C-Extensions.html">Extensions to the C Language Family</a> &nbsp; [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="Indices.html" title="Index" rel="index">Index</a>]</p>
</div>



</body>
</html>
